-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
umpf: answer interactive prompts with default when --default set #50
Conversation
I think a |
Ok, but doesn't it make sense to have piping yes behave as expected as well? |
Fair point. I would rename the option then though. How about |
Sounds good. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a few, mostly cosmetic things left.
When building or tagging an umpf, umpf can ask which branch to use when multiple are available. Piping yes(1) into umpf in this case doesn't work, because the variable populated by read in that case is left empty. Provide for this use case, a --default option that will take a default if one is known. Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good now, thanks.
When building or tagging an umpf, umpf can ask which branch to use when multiple are available. Piping
yes(1)
into umpf in this case doesn't work, because the variable populated by read in that case is left empty.Handle this case to reduce user confusion.